docs(vm): correct overcommit defaults and warn about aggressive CPU ratio#1077
Open
abonillabeeche wants to merge 11 commits into
Open
docs(vm): correct overcommit defaults and warn about aggressive CPU ratio#1077abonillabeeche wants to merge 11 commits into
abonillabeeche wants to merge 11 commits into
Conversation
…tenments Update the Volumes tab guidance to recommend the SCSI bus (virtio-scsi) for Windows workloads that do sustained writes; virtio-scsi supports multiple queues and has a more efficient DISCARD path than virtio-blk. Clarify that the Cloud Config field is processed on Windows images that include Cloudbase-Init (rather than being ignored outright). Note that after VMDP is installed the network model can be switched from e1000 to virtio for better throughput. Add a new "Recommended Tuning" section documenting KubeVirt's Hyper-V TLFS enlightenments as a suggested performance tuning for Windows guests, with the full YAML block and a verification command. Signed-off-by: Alejandro Bonilla <[email protected]>
…atio Updates the Resource Overcommit page to reflect the current defaults shipped in Harvester v1.8+: - CPU allocation ratio: 1600% -> 1000% - Storage allocation ratio: 200% -> 100% Adds a note that the default CPU allocation ratio of 1000% is aggressive and can produce noticeable CPU steal and latency spikes in guests. Encourages benchmarking vCPUs for latency-sensitive or sustained CPU-bound workloads and suggests a conservative starting point of 200-400%. Also adds a note on the Virtual Machines landing page pointing users at the Resource Overcommit page before creating VMs so that the allocation ratios can be reviewed against workload requirements. Signed-off-by: Alejandro Bonilla <[email protected]>
Co-authored-by: Jillian Maroket <[email protected]> Signed-off-by: Alejandro Bonilla <[email protected]>
Co-authored-by: Jillian Maroket <[email protected]> Signed-off-by: Alejandro Bonilla <[email protected]>
Co-authored-by: Jillian Maroket <[email protected]> Signed-off-by: Alejandro Bonilla <[email protected]>
Co-authored-by: Jillian Maroket <[email protected]> Signed-off-by: Alejandro Bonilla <[email protected]>
Co-authored-by: Jillian Maroket <[email protected]> Signed-off-by: Alejandro Bonilla <[email protected]>
Co-authored-by: Jillian Maroket <[email protected]> Signed-off-by: Alejandro Bonilla <[email protected]>
Co-authored-by: Jillian Maroket <[email protected]> Signed-off-by: Alejandro Bonilla <[email protected]>
Co-authored-by: Jillian Maroket <[email protected]> Signed-off-by: Alejandro Bonilla <[email protected]>
Co-authored-by: Jillian Maroket <[email protected]> Signed-off-by: Alejandro Bonilla <[email protected]>
|
Tick the box to add this pull request to the merge queue (same as
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two related documentation fixes on the VM Management pages.
1. Resource Overcommit — defaults are wrong
The Resource Overcommit page still shows the pre-v1.8 defaults. The current values in `pkg/settings/settings.go#L46` are:
```
{"cpu":1000,"memory":150,"storage":100}
```
The doc is updated accordingly:
The change from `1600 → 1000` and `200 → 100` landed for v1.8.0 (verified against tags `v1.7.2` vs `v1.8.0`).
2. Encourage benchmarking vCPUs
A note is added to the Resource Overcommit page explaining that the default CPU allocation ratio of 1000% is still aggressive — under load it can produce noticeable CPU steal and latency spikes in guests. The note recommends benchmarking with a representative workload for latency-sensitive or sustained CPU-bound workloads and suggests a conservative starting point of 200–400%.
3. Point users at Resource Overcommit before creating VMs
A short note is added on the Virtual Machines landing page so users are steered to the Resource Overcommit page before creating VMs.
Both `docs/` and `versioned_docs/version-v1.8/` are updated.
Test plan